Appendix - Troubleshooting Logi Log Files

Note:  These instructions apply only to Windows installations under IIS.

When troubleshooting Logi, the first thing to try is setting the Debug Dashboard and Embedded Reports application setting to True (see Application Settings: Dashboard and Reports Tab). This allows the reports and dashboard panels to output errors with debug level information if they generate errors. If this does not generate the information necessary to resolve the problem, it can sometimes be helpful to enable debugging at a lower level to allow the web server to show the actual error the application is experiencing at the web server level. To configure this:

  1. Browse to the Logi\_Definitions directory under the installed directory for your Keyfactor Command implementation. By default, this is:

    C:\Program Files\Keyfactor\Keyfactor Platform\Logi\_Definitions
  2. Using a text editor opened with the “Run as administrator” option, open the _Settings.lgx file for editing.
  3. Find the <General> section and within this the rdDebuggerStyle="Redirect" setting.

    Copy
    <General BookmarkCollectionDefault="Bookmarks-@Function.UserName~" BookmarkLocation="@Function.AppPhysicalPath~\SavedBookmarks" rdDebuggerSecurityRightID="Administrator"
              rdDebuggerStyle="Redirect" RedirectErrorUrl="_Definitions/_Reports/Error.aspx" RepoFriendly="True" ScriptingLanguage="JavaScript">
        <WaitPage />
    </General>
  4. Change rdDebuggerStyle="Redirect" to rdDebuggerStyle="DebuggerLinks".

    Copy
    <General BookmarkCollectionDefault="Bookmarks-@Function.UserName~" BookmarkLocation="@Function.AppPhysicalPath~\SavedBookmarks" rdDebuggerSecurityRightID="Administrator"
              rdDebuggerStyle="DebuggerLinks" RedirectErrorUrl="_Definitions/_Reports/Error.aspx" RepoFriendly="True" ScriptingLanguage="JavaScript">
        <WaitPage />
    </General>
  5. Save the changes and then reproduce the problem.
  6. If you have also enabled the Debug Dashboard and Embedded Reports application setting, you can try to access the debug output in usual way supported by that application setting (see Application Settings: Dashboard and Reports Tab).
  7. If you have not enabled the Debug Dashboard and Embedded Reports application setting or the debug output does not appear in the expected locations in the Management Portal, look for the debug output in the Logi\rdDownload directory under the installed directory for your Keyfactor Command implementation. By default, this is:

    C:\Program Files\Keyfactor\Keyfactor Platform\Logi\rdDownload
  8. Tip:  If you do not find debug output when running a report manually in the Management Portal, try scheduling a report for delivery via email or saving to disk using the Report Manager. Debugging operates differently for these two modes of running a report.
    Note:  When the portal experiences a 500 error, Logi logs will not be written to the usual output directory.